[17:11] Samantha Wright: Okay. Let's get rolling. [17:12] Samantha Wright: For those of you not familiar with this face of mine, I'm Dr. Samantha Wright, the current CTO of Nanite Systems Consumer Products. I took over development of SXD maintenance and the SXD² project back in late 2014 when Koichi Santei finally retired. [17:13] Samantha Wright: Today we'll be covering everything you need to know to survive with one of our robot systems, whether as a unit, a casual user, or an owner. [17:13] SXD an1ka waves one of her arms to the crowd uselessly, face still stuck to the metal surface she's laying on. "And this unit is... unable to see much beyond the table. Helloooo." [17:13] Samantha Wright: I think just about everyone—except maybe kir0bea and ely5ia—will get something out of this. [17:13] Samantha Wright squints at the tabled SXD. "Noisy!" [17:14] Presentation: Slide 2 [17:14] SXD an1ka: Do not worry, kir0bea will get what is coming to her. [17:14] Samantha Wright: By the time we're done here, you'll hopefully have a sense of how to operate and control your unit through both the command line and the menu system. [17:15] Samantha Wright: I'll be posting the slides and a transcript of this chat on our support website (support.nanite-systems.com) after the Q&A period is finished. [17:15] Presentation: Slide 3 [17:15] DAX/2 mir4nda r0xanne: Feel like I'm back in a college class again [17:15] NS m4tild4 wiggles with excitement [17:16] Samantha Wright: And even if you really, really hate our company for some reason and have no interest or chance of ever interacting with one of *our* robots, as long as you like robots in general I'm sure there'll be some inspiration material in here somewhere. [17:16] Presentation: Slide 4 [17:16] SXD an1ka: You will also be given a complimentary fruit basket fashioned from the folded-up slides of the presentation, as long as supplies last. [17:16] SXD an1ka: Supplies have expired. [17:17] Samantha Wright: First things first: like most toys in SL, clicking stuff gets you a menu. There are a few reasons this might not work, though, which we'll be discussing later. [17:17] Samantha Wright: About half of our controller designs have touch screens as of version 8.0.0. ... Sadly these are fairly annoying and hard to poke at, but we'll see what we can do about that in the distant future. [17:17] Presentation: Slide 5 [17:18] Samantha Wright: Units themselves also have one extra way of using the system, through the local HUD. [17:18] SXD an1ka: Robots do not wish to sit still for the screens to be touched sufficiently. [17:18] Samantha Wright: Clicking the logo at the far left will get you the main menu. Each section represents a device, with the largest generally being the system section. [17:18] Samantha Wright: The most important device section is the battery: the bar on the top tells you how much power you have left, and the bar on the bottom reports how quickly you're using power. [17:19] Presentation: Slide 6 [17:19] Samantha Wright: So let's talk about power, actually. [17:19] Presentation: Slide 7 [17:19] Samantha Wright: The oldest—and perhaps defining—feature of our system is that you can turn bits and pieces of it on and off as needed to save power. There may be some other systems that do this now, but we were, I think, the first. [17:20] SXD an1ka: This unit has disabled its margarita maker to conserve energy. [17:20] Samantha Wright: Some of the features don't actually eat power always, like voice and teleport; those subsystems only use power when they're in used. [17:20] Presentation: Slide 8 [17:20] E.m.i.l.i.e.: I wanted a margarita though [17:21] Samantha Wright: If you open the subsystems menu, this is what you'll see. Some are tucked away under the network submenu; most aren't. [17:21] Samantha Wright: The teleport subsystem takes a few seconds to recharge after TPing, anywhere from 2 to 10 seconds depending on distance. [17:21] Samantha Wright: Usually, if you go between sims, it will take the full 10 seconds. [17:22] Samantha Wright: You'll also find that, after teleporting, you can't seem to touch or sit down on things for a bit. [17:22] Samantha Wright: This isn't actually true, though; you're just limited to touching things that are within arm's reach. [17:22] Presentation: Slide 9 [17:24] Samantha Wright: There are some underlying differences in how the subsystems actually work. [17:24] Samantha Wright: If you click on 'volume' or 'motors' in the menu, for example, you'll cycle through several states. [17:24] Presentation: Slide 10 [17:24] Samantha Wright: Those of you with control systems will recognize this screen. [17:24] SXD an1ka: This unit suggested a sacrifice to one or more gods before the slide show began to ensure it going well, but was ultimately ignored. [17:25] Samantha Wright: It's what you get for typing '@power status' or pressing the 'status' button. [17:25] Samantha Wright: The speech and motors subsystems are broken down into their components, [voice; preamplifier; power-amplifier] and [move; rapid]. [17:26] Presentation: Slide 11 [17:26] Samantha Wright: So where does all this power come from? From your battery, of course! [17:26] SXD an1ka whispers: System halted. [17:27] Samantha Wright: an1ka here has a 13-7026-S, which is a type of sonofusion battery. [17:27] Samantha Wright: It lasts just over 24 hours if you make a consistent draw of 780 W. [17:27] Samantha Wright: Of course, in reality, you may go through it more quickly than that if you use a lot of teleporting and running and talking. [17:28] Samantha Wright: Similarly, you can stretch it up to 20x if you do nothing at all and go into sleep mode, so an1ka's battery can last almost 3 weeks. [17:28] DAX/2 s0phie: Query: [17:28] SXD an1ka whispers: Initializing... [17:28] Samantha Wright: ...This one is actually a bit old, but on the plus side it has no chance of causing a grey goo outbreak. [17:28] SXD an1ka: Hello world. [17:28] Samantha Wright: Yes, s0phie? [17:29] DAX/2 s0phie: Does speech consume power even if it somehow magically comes directly from the unit's own mouth, and not through the pipeline? [17:29] 11543: Such as this? [17:29] Samantha Wright: Ah. No; the technical answer is that doing so would require a listener on channel 0, which eats up a ton of script time and is generally frowned upon. [17:30] Samantha Wright: The less technical answer is that I never thought of it. [17:30] DAX/2 s0phie: Acknowledged. [17:30] Samantha Wright: When you put on your controller or log in, it will emit something like "Waiting to detect devices; please wait." [17:30] Samantha Wright: It can take up to 30 seconds, which is a bit maddening. [17:31] Samantha Wright: Unfortunately this is necessary to try and reduce the risk of the controller failing to detect the battery after logging in. [17:31] Samantha Wright: I'm still experimenting with ways to improve the recognition process, but a sufficiently slow computer and a sufficiently busy sim will almost always cause grief. [17:32] Samantha Wright: Oh. Also, you can disregard everything about power if you're using one of our new Barthes Asset Control disk drives. [17:32] Samantha Wright: They simply don't use power at all. [17:32] Presentation: Slide 12 [17:32] Samantha Wright: Okay... on to charging. [17:32] Samantha Wright: We have... many different kinds of charger that you can use, some of which you've probably never even seen before. [17:33] Samantha Wright: There are four categories of charger: ACS, UMD, NS active, and NS passive. [17:34] Samantha Wright: Unfortunately I don't have any UMD chargers to demonstrate with; if any of you visit the House of Qetesh, however, you may find some there. [17:34] Samantha Wright: As for the others... [17:35] ely5ia: May this unit use one of the presentation chargers? [17:35] Samantha Wright: Certainly, ely5ia. [17:35] Samantha Wright: These four pads represent the NS active chargers; the big one is outdated and pretty rare now. [17:35] ely5ia: Thank you. [17:35] Samantha Wright: The tesla coil behind them is a Wireless Charging Node; they're automatic and very convenient. Unless you don't want to charge. [17:35] Charger 3 whispers: Connected to civilian controller SXD ely5ia. [17:35] SXD ely5ia connects to external power from the Charger 3. [17:35] SXD ely5ia whispers: Motor locks engaged. [17:36] SXD ely5ia whispers: Charging initiated. Disabling high-draw subsystems. [17:36] Samantha Wright: The induction chargers built by the Field Robotics Group—those are the other three here—may seem a little confusing to use at first because of the holographic screens, but they're very handy in the long term. [17:37] Samantha Wright: Here's an ACS active charger; it uses the same protocol as our chargers and can be found in some older sims, although it's slower. [17:37] SXD ely5ia whispers: Charge cycle complete. Enabling high-draw subsystems. [17:38] SXD ely5ia whispers: Motor locks disengaged. [17:38] SXD ely5ia disconnects from the Charger 3. [17:38] Samantha Wright: And here... is a Destruir Technologies wireless charging station made by Lucian Underwood. Using these is a bit of a hassle for ACS units, but for NS units it's pretty painless. Unlike our new WCNs, you must click on the WCS to start charging, and by default they disconnect when charging is finished. [17:38] E.m.i.l.i.e.: is there a way to adjust the height on the chargers? [17:38] Samantha Wright: Good question! No. [17:38] Samantha Wright: ...There should be, though, shouldn't there? [17:39] Samantha Wright nods to herself, staring off into the distance. [17:39] E.m.i.l.i.e.: nod nod [17:39] Samantha Wright: When we release the military system, we plan on adding a new kind of charger. Perhaps the codebase will be due for a refresh then. [17:39] Samantha Wright: There are other kinds of chargers that we make, based on code that's fairly easy to copy... [17:40] Samantha Wright: Here's a display case, like you might see here on floor 1 or 5. [17:40] Samantha Wright: They charge at 780 W/sec, so they freeze your battery level in place unless you lower your usage. [17:40] E.m.i.l.i.e.: so handy for afk [17:40] Samantha Wright: The demo stands work similarly. [17:41] Samantha Wright: If you'd like to make your own passive charger, you can get the code from the SDK box on the 3rd party products table on the ground floor. [17:41] Samantha Wright: Anyway. Tidying all that up. [17:41] Presentation: Slide 13 [17:42] Samantha Wright: As your battery runs down, you'll notice a few things, which are described here on the slide. [17:43] Samantha Wright: Credit for the 5% shutdown threshold idea goes to ely5ia here. [17:43] Samantha Wright: When you hit 5%, the system will shut down after 30 seconds; you can abort this with the @shutdown command if you know the parameters. [17:43] Presentation: Slide 14 [17:43] Samantha Wright: Okay. New subject. [17:43] ely5ia: This prevents units from running entirely out of battery and being stranded while AFK. [17:43] Presentation: Slide 15 [17:44] Samantha Wright: The cortex is the part of the system that controls (almost) everything related to speech. The most fundamental feature of this ensemble is the chat redirect, which you can turn on and off with some fairly easy commands. [17:46] Samantha Wright: It can be important to be able to escape the redirect quickly if you need to issue a command to an old object that listens for commands from avatars only, or want to talk OOCly. [17:46] DAX/2 s0phie: This unit recalls a statement that lecture notes will be available on blackboard in three to four weeks, dependent upon homework load. [17:46] Presentation: Slide 16 [17:46] Samantha Wright: You may also find, sometimes, that the redirect gets in the way of typing on channels... more on that later. [17:47] Samantha Wright: Personas are the original purpose of the cortex, and the other oldest feature of the system. [17:47] Samantha Wright: Sometimes a robot who's just a robot is just boring. [17:47] t3z: Authorization check failed. [17:47] E.m.i.l.i.e.: Authorization check failed. [17:47] NS m4tild4: Authorization check failed. [17:47] DAX/2 Moobot-Miya-9056: Authorization check failed. [17:47] NS B o n n Y: Authorization check failed. [17:47] SXD ely5ia: Authorization check failed. [17:47] Nyame Wolfsong (hypnoneko): Authorization check failed. [17:47] NS Equu3a: Authorization check failed. [17:47] DAX/2 s0phie whispers: Personality 'playful' activated. [17:47] DAX/2 kir0bea whispers: Personality 'playful' activated. [17:47] E.m.i.l.i.e.: I prefer "android" it's classier [17:47] Samantha Wright: So why not go a step further? [17:47] DAX/2 kir0bea giggles. [17:47] SXD ely5ia: Sometimes. [17:48] DAX/2 s0phie: Okay! [17:48] DAX/2 s0phie: Um. I don't get it? [17:48] DAX/2 kir0bea whispers: Default personality restored. [17:48] Samantha Wright: Ah, fun point about the word 'android.' We generally recommend the word 'gynoid' for units that are intended to resemble females, based on the Greek origins of the word: ανδρος = man, γυνη = woman. [17:49] Samantha Wright: I suppose the gender-neutral term would be 'anthroid', but most people would assume that means anthropomorphic animal-oid. [17:49] E.m.i.l.i.e. scribbles notes down [17:49] Samantha Wright: So... often we just say 'synthetic' as a catch-all term. [17:49] Samantha Wright: Or, of course, 'unit.' [17:49] DAX/2 s0phie: There are a few units that can be sticklers about that, too. [17:50] Samantha Wright: Indeed! Indeed. [17:50] SXD an1ka whispers: Personality 'uncoupled' activated. [17:50] SXD an1ka loses all grace and refined coordination, becoming mildly slumped and lazy as the command is input. [17:50] SXD an1ka soon develops a shocked expression that a discordant flood of hopeless, scrambled thoughts which give way to an odd look of apathetic and listless lack of direction. Never has a synthetic looked more like a lost and confused child. [17:50] SXD ely5ia: This synthetic is not certain which it prefers. [17:50] SXD an1ka: This unit believes Trump knows what is best for America. [17:50] E.m.i.l.i.e.: I'm usually dealing with humans so still feel android is better than robot [17:50] E.m.i.l.i.e.: but I understand when you're around lots of different types like here [17:51] DAX/2 s0phie giggles. "Well played, demonstration unit." [17:51] DAX/2 robot horse: The best i can expect from most ponies is android. usually its robot [17:51] Samantha Wright: Well, it should be equoid! [17:51] Samantha Wright: Or... hippoid... but THAT will definitely cause confusion. [17:51] Samantha Wright hmms. [17:51] DAX/2 s0phie continues to giggle profusely. [17:51] DAX/2 Moobot-Miya-9056: Moo. [17:52] E.m.i.l.i.e.: mooboid? [17:52] Samantha Wright: Personas do up to four things: they load matching RLV folders, change how you sound when talking, trigger a script containing pre-recorded actions or system commands, and, maybe most interestingly, alter the cortex's preset messages. [17:52] Presentation: Slide 17 [17:52] Samantha Wright: When the mind subsystem is turned off, the unit can't think clearly enough to form arbitrary sentences. You're limited to prerecorded quotations. [17:52] Samantha Wright: You can see a list of these by typing: .info [17:53] DAX/2 s0phie: Gee, thanks! [17:53] Samantha Wright: All of them start with dots, to prevent confusion with everything else. [17:53] Samantha Wright: And, to ham it up, you can use these even when your mind is on. [17:53] DAX/2 kir0bea: .yes [17:53] Samantha Wright: The defaults are pretty plain, although every model has its own unique set. [17:53] DAX/2 kir0bea: Welp. [17:53] SXD ely5ia: Acknowledged. [17:53] SXD ely5ia: Humor detected. [17:53] DAX/2 kir0bea: It's .y and .n [17:53] DAX/2 s0phie: .dance [17:53] DAX/2 s0phie: Yeah, let's dance! [17:53] DAX/2 kir0bea frowns at the presentation. [17:53] SXD an1ka: Yes, fine. [17:54] SXD an1ka: Goodbye already! [17:54] Samantha Wright: Different personas may use different commands, so look them up before trying to use them. [17:54] SXD an1ka: Ugh... I can't! [17:54] DAX/2 Moobot-Miya-9056: Yes. [17:54] SXD an1ka: Huh. Can't do that, either. [17:54] SXD an1ka: I can't help myself... I-I need to dance. [17:54] DAX/2 s0phie: Um. My head feels funny. [17:54] Samantha Wright: The standard EVALLOOP persona is a good example of this. [17:54] SXD an1ka: Maybe if we fuck this will go away. [17:54] SXD an1ka: Agh! I'm broken! [17:54] SXD an1ka: Please enable the MIND module for further interactivity. [17:54] Samantha Wright: Also, every unit has a slightly different default persona. [17:54] NS m4tild4: question [17:54] Samantha Wright: Aides ask if you need care, for example, rather than help. [17:54] Samantha Wright: Yes? [17:55] SXD an1ka: This unit likes alphabet soup, for its inherent endless mysteries. [17:55] NS m4tild4: To look up the commands, do we just need the notecard handy? or can we see them through the menu system? [17:55] Samantha Wright: You can get a list of preset messages by typing .info [17:55] Samantha Wright: For all system commands, try: @commands or @help [17:55] SXD an1ka whispers: Default personality restored. [17:56] NS m4tild4: Ah okay that changes based on the persona then? [17:56] Samantha Wright: We'll be talking more about real system commands later. [17:56] Presentation: Slide 18 [17:56] Samantha Wright: Okay. Next big feature. [17:56] Samantha Wright: This one was so big, actually, we had to put it into two modules, not just one. [17:57] Samantha Wright: If you want to suppress the noise you make when you talk, type #@! somewhere in it. [17:57] Samantha Wright: That will suppress the speech marker noise. [17:57] Samantha Wright: ...Either s0phie or ely5ia asked for that. Maybe both. [17:57] SXD ely5ia: This unit does not recall. [17:57] Samantha Wright: Long time ago. Longgg time ago. [17:57] DAX/2 s0phie shakes its head. [17:58] Samantha Wright: The next big feature of the control system was the whole point of version 8.2, which is the speech pipeline. [17:58] Samantha Wright: The speech pipeline is a collection of filters that let you or one of your asshole friends make your talk sound funny. [17:59] NS m4tild4: Humor detected. [17:59] E.m.i.l.i.e.: I have one of those friends! [17:59] Samantha Wright: They're always processed in order, to prevent them from receiving text they can't parse properly. [17:59] Presentation: Slide 19 [18:00] SXD an1ka: This unit once saw a badger. On recollection, it may have been a printer. [18:00] Z3PH-YR is online. [18:00] Samantha Wright: There are a couple of related features in the 'cortex' menu: a toggle that decides whether the unit may use !release, and a special thing called gag mode, which is also called the output pipe. [18:01] Samantha Wright: The idea behind the output pipe was to detect other RLV devices, like gags, block them from listening to the user directly, and redirect the controller's output into them. Like a shim. [18:01] Samantha Wright: Unfortunately it doesn't work with most gags, but it does work with our remote console, which we'll be talking about later. [18:01] Samantha Wright: Eventually we'll probably make more devices that work with this functionality. [18:01] Samantha Wright: If you have any trouble speaking, hit the 'clear' or 'reset' button. [18:02] Samantha Wright: The clear button disables all filters, and the reset button will actually try to reset their scripts in case of crashes or an infinite loop. [18:02] Presentation: Slide 20 [18:02] Presentation: Slide 19 [18:02] SXD ely5ia: This unit would like to suggest having reset recheck for gags. [18:02] Presentation: Slide 20 [18:02] Presentation: Slide 21 [18:03] Samantha Wright: Probably a good idea, although it actually listens constantly. [18:03] SXD ely5ia: To account for weirdness wherein a gag is not present but the cortex believes it is. [18:03] E.m.i.l.i.e.: I've managed to get everything to work except polyglot [18:03] Samantha Wright: Most of the filters that come with the system can take parameters; here are some examples of the correct formats. [18:04] Samantha Wright: If you press the add+config button or the configure button and type 'help', it'll tell you the right format. [18:04] Samantha Wright: The polyglot filter is a bit of a pain; its purpose is to translate between languages. [18:04] DAX/2 kir0bea: This unit has not managed to successfully use the polyglot, either. [18:05] Samantha Wright: The web translation service we use caps out at about 1000 messages per day, should be unique to each user's key, and takes ISO-639-1 two-letter name codes: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes [18:05] Samantha Wright: And I have no idea why it sometimes seems to not work and then ... later decides to. [18:05] DAX/2 Moobot-Miya-9056: testing polyglot one two three [18:05] SXD an1ka: That tickles. [18:05] SXD an1ka: Filter probe initiated; chain cleared. [18:05] SXD an1ka: Filter activated: fl_polyglot. [18:06] Samantha Wright: The default translation should be en|es. [18:06] SXD an1ka: This is a unfortunate exemption. [18:06] Samantha Wright: Which would be English to Spanish. [18:06] Samantha Wright: And... yeah, I'm not sure what the magic is to make it work. [18:06] Samantha Wright: Sometimes the translation server seems to just give up and return the original English. [18:06] DAX/2 s0phie: Interesting. [18:06] DAX/2 Moobot-Miya-9056: Moo. [18:06] Samantha Wright: So... don't worry about that too much. It's not just you. [18:07] Samantha Wright: In the meantime, play with the Barnyard filter. [18:07] SXD an1ka: Filter deactivated: fl_polyglot. [18:07] SXD an1ka: Filter activated: fl_barnyard. [18:07] SXD an1ka: Mooo moo mooo moo moooooooooooo moo moo moo moooooo moooooooooo mooooooo. Mooo moooooo moo 4032 moooooo moo moooooooo moooo moooo. [18:07] DAX/2 kir0bea: Please do not. [18:07] E.m.i.l.i.e.: when in doubt, talk gibberish! [18:07] SXD an1ka: Filter deactivated: fl_barnyard. [18:07] NS m4tild4: ʷᵒʷ ᵈᶦᵈᶰ'ᵗ ᵉᵛᵉᶰ ᵏᶰᵒʷ ᵗʰᵉˢᵉ ʷʰᵉʳᵉ ᶦᶰ ʰᵉʳᵉ [18:07] Samantha Wright: The only thing the default filter package is really missing is something that sounds like your mouth's full... [18:07] Presentation: Slide 22 [18:07] DAX/2 kir0bea: Yes. [18:08] E.m.i.l.i.e.: I think that's covered under lisp? [18:08] Samantha Wright: Thort of. [18:08] DAX/2 kir0bea: Lisp is a lazy method. [18:08] SXD an1ka: This has been a demonstration of the non working translation function. What follows is 4032 minutes of screaming white noise. [18:08] E.m.i.l.i.e.: isth closth [18:08] Samantha Wright: Anyway. Congrats on making it this far; we're about half way through the slides now and about half way through our time. [18:08] t3z: Maybe drunk filter for excessive lubricant usage? [18:08] Samantha Wright: If anyone would like to go take a lube break or something for ten minutes, be my guest. [18:08] DAX/2 kir0bea: Yes. [18:09] Samantha Wright: Because... two hour lectures with no breaks are murder. [18:09] Trinket is online. [18:09] DAX/2 Moobot-Miya-9056: Moo. [18:09] Samantha Wright: The remaining subjects we have to cover are access/user management, the command line, and file and package management. [18:09] t3z: Not as bad as lecturing for 2 hours :) [18:09] DAX/2 s0phie: This unit recalls a three hour twice a week summer course over Introduction to Proofs. [18:10] DAX/2 s0phie: With no breaks. [18:11] Samantha Wright: That's pretty agonizing, but I suppose you might end up knee-deep in the dead during it and not have any conveniently-placed break times. [18:12] DAX/2 s0phie nods. [18:12] NS m4tild4: I dint think I've manged to get below 60% yet [18:13] Samantha Wright: We have a lot of wireless chargers here, so that's plausible. [18:13] Niadra: Wires for Nia? [18:14] Samantha Wright: Wires for Nia. [18:14] Niadra: ^,..,^ [18:18] Samantha Wright: Okay. Back to it. [18:18] Presentation: Slide 23 [18:18] Samantha Wright: User management is mostly painless, but there are a couple of pieces of terminology you need to know. [18:19] Samantha Wright: Managers are comparable to OpenCollar's secowners: you can do most things, but you can't usurp owners and are at their mercy. [18:20] Samantha Wright: Basic users, however, are a bit different; because the controller is normally publicly accessible for most features, they offer an alternative to being truly public. They cannot mess with your settings or steal you or anything, though. [18:20] Samantha Wright: manage › users gets you a list of usernames; clicking a user's name will get you a dialog with remove, promote, demote, and submit buttons. [18:21] Samantha Wright: Promote/demote move up and down one level of power, and submit makes someone your only owner. [18:21] Presentation: Slide 24 [18:21] Samantha Wright: Any owner can press the submit button, so be careful. [18:21] Samantha Wright: Also, owners may remove each other. [18:21] DAX/2 kir0bea: Oh,. there is a level above manager level 1? [18:22] DAX/2 kir0bea: This unit had never bothered checking... [18:22] Samantha Wright: Owner = 2, manager = 1, user = 0. [18:22] NS m4tild4: when first using it I pressed submit thinking it was to apply changes. thankfully it gave me errors about invalid permissions [18:22] Samantha Wright: Yes, it can be a bit tricky. I spent forever trying to think of a single word that explained what the button did. [18:22] DAX/2 kir0bea: Yes, m4tilda, this unit did that as well. [18:22] Samantha Wright: If you can think of a better one that'll fit on the button, lemme know. [18:22] SXD 999-63-2760: Claim. Set Owner. [18:23] Samantha Wright: Earlier when we were talking about personas, most of you received a message saying I wasn't allowed to access your systems. That may be surprising if you have the default access settings, which permit local use. [18:23] Samantha Wright: Claim is transitively backward. Set owner might do. [18:23] Samantha Wright: Remote and local access are separate; local access can only be used within 10 m. Remote access can be used anywhere in the sim. [18:24] Nyame Wolfsong: Give up! [18:24] Samantha Wright: By default, remote access should be available to all registered users. [18:24] Samantha Wright: Previously, this was owner-only. [18:24] Samantha Wright: ...But it was a hassle for tech support. [18:24] Samantha Wright: Self access is also controlled through the manage › access menu. [18:26] Samantha Wright: Turn it off, and you're completely locked out. Hope you set other owners! [18:26] Presentation: Slide 25 [18:27] DAX/2 kir0bea: Or just use @safeword [18:27] Samantha Wright: Another great way to screw yourself over is to forget your PIN. This presents local access. [18:27] Samantha Wright: Locking the controller from the access menu will prompt for a PIN before the controller can be touched again. [18:28] Presentation: Slide 26 [18:28] Samantha Wright: But yes, speaking about @safeword. [18:28] Samantha Wright: That will fix the self-access problem, with the price of telling all your owners that you messed up, just like how an OpenCollar tattles if you turn off RLV. [18:29] Kazuma Onizuka entered the region (41.38 m). [18:29] Samantha Wright: They'll also be told if you use @keychain reset to ditch them, but not if you remove them normally through the menu because you have the power to do so. [18:29] E.m.i.l.i.e.: can you target the @zap at someone or does it hit everybody? [18:29] Samantha Wright: You can target it, yes. [18:29] Samantha Wright: You need to know their serial number, though. [18:30] Samantha Wright: The syntax is: @zap [18:30] Samantha Wright: If you're not a robot, though, or you have a lot of people you want to recharge, you can also buy a pulse charger. [18:30] NS Pulse Charger 97-0032-F (Demo Unit) whispers: Nanite Systems pulse charger 97-0032-D. Warning: disable sensitive electronics before firing or permanent damage may occur. [18:30] Samantha Wright: These are not recommended as replacements for normal chargers. [18:30] Samantha Wright: And people will get VERY ANGRY at you for using them. [18:30] DAX/2 kir0bea winces. [18:30] NS Pulse Charger 97-0032-F (Demo Unit) whispers: Discharge complete. [18:30] DAX/2 Moobot-Miya-9056: Moo. [18:30] Samantha Wright: They also take a long time to recharge after firing. [18:31] NS Pulse Charger 97-0032-F (Demo Unit) whispers: The pulse charger is now ready to fire. [18:31] t3z: Bibble bibble.... [18:31] E.m.i.l.i.e.: wow yay full power! [18:31] Samantha Wright: But they do recharge everyone in the whole sim, so that's neat! [18:31] DAX/2 kir0bea: Oh, the whole sim? [18:31] DAX/2 s0phie: Query: [18:31] DAX/2 kir0bea: This unit thought only within 20m or something arbitrary like that. [18:32] DAX/2 s0phie: Why do pulse chargers make people "VERY ANGRY"? [18:32] Samantha Wright: Well, they do so much charging most units go into a fault and fall down. [18:32] Samantha Wright: Also they're hideously loud. [18:32] NS m4tild4: Oh! good to know [18:32] Presentation: Slide 27 [18:33] Samantha Wright: Okay. Command line. [18:33] Presentation: Slide 28 [18:33] SXD 999-63-2760: As this unit recalls, they also cause interference with some systems. [18:33] Samantha Wright: Not yet. As ATOS develops further I'll probably work on balancing out stuff like what happens when you get a huge hit of power. [18:34] Samantha Wright: In the old days, ! commands were pretty common and important; nowadays they're quite relegated. There isn't even really a complete list we publish anymore; I'll have to fix that. [18:35] Samantha Wright: Mostly it's about @ commands these days, which are smarter and can be interpreted by any device or program known to the controller. [18:35] DAX/2 s0phie looks around for a suspicious cardboard box. [18:35] Presentation: Slide 29 [18:35] kir0bea: (( I can only think of !fault and !fan and !working/done )) [18:35] Samantha Wright: The most important cortex commands are here; besides from !light, they're mostly useful for RP. [18:36] SXD 999-63-2760: Some units will !spark upon any mistake that should not be possible. [18:36] Samantha Wright: Yes, good point about best RPing practice. [18:36] Samantha Wright: If you make a typo—robots shouldn't make typos! [18:36] Samantha Wright: You must be broken. [18:36] E.m.i.l.i.e.: clearly [18:36] Samantha Wright: !spark or !fault as you see fit before making a correction. [18:36] SXD 999-63-2760: And this unit will one day get you to correct the issue with its oem. [18:37] kir0bea: (( Unknown cortex command: !light Consult user manual. )) [18:37] Miya: ((same)) [18:37] Samantha Wright: Right; the !light command only works with parameters. [18:37] Samantha Wright: It sends messages directly to your devices. [18:37] Samantha Wright: Type, for example, !light off [18:37] Samantha Wright: Poof, your devices powered down. [18:37] Samantha Wright: Now try !light on [18:37] Samantha Wright: Hey! They're back! [18:38] Samantha Wright: That's sort of a developer thing that most people don't need much. [18:38] Samantha Wright: There's a list of most 'light bus' commands here: http://develop.nanite-systems.com/?light_bus [18:38] DAX/2 kir0bea: light off is useful for removing akashic icons. [18:38] Samantha Wright: Yes, you can use it to remove devices. [18:38] Samantha Wright: Especially OSL elements, which don't show up in the device menu. The device menu also has a separate 'remove' button for things like icons. [18:39] DAX/2 kir0bea: Ooh. [18:39] DAX/2 kir0bea nods. [18:39] NS m4tild4: huh !light off turned off my shield [18:39] Samantha Wright: Yes. Shields don't work when you're powered down. [18:39] Samantha Wright: Most of the other bang commands just play sound effects, derived from your system's status voice: !love, !love2, !love3, !love4, !greet, !greet2, !bye. [18:40] Samantha Wright: The only one I haven't mentioned is !fan, which takes either a word like: idle, low, med, high, max, or a number from 0 to 100. [18:40] Samantha Wright: For those of you with SXD and full DAX/2 controllers, these are useful! [18:40] Samantha Wright: Aide units will also make more or less noise. [18:41] Presentation: Slide 30 [18:41] Samantha Wright: But bang commands are fairly limited; most interesting features are in the @ command set. [18:41] Samantha Wright: There are many, many @ commands. In fact, you can get a list just by typing: @commands [18:42] Samantha Wright: Many commands will tell you how to use them if you just type their name, e.g. @persona. [18:42] Samantha Wright: For some you have to type @help [18:42] Samantha Wright: The @help manual isn't quite done yet, but it's already pretty useful for some things. [18:42] Presentation: Slide 31 [18:43] Samantha Wright: If you're not the unit, your primary way to use these commands is through a remote access HUD like this one. We sell them for L$200 with transfer permissions, so you can give them to your owner. [18:43] Samantha Wright: The 'open console' button uses RLV to send commands directly to the unit, which is handy. [18:44] NS Remote Console: Connecting to DAX/2 kir0bea... [18:44] DAX/2 kir0bea: Connected on 998273395 GHz. [18:44] DAX/2 kir0bea: Terminal open. Your input will now be sent to the unit. Type 'help' for a list of supported commands. [18:44] DAX/2 kir0bea: This unit likes big butts and it cannot lie. [18:44] DAX/2 kir0bea: You other units cannot deny. [18:44] DAX/2 kir0bea: Terminal closed. [18:44] DAX/2 kir0bea nodnods. [18:44] Samantha Wright: Plenty of opportunities for broadcasting lewdness. [18:44] Presentation: Slide 32 [18:45] Samantha Wright: Commands can also be saved into text files which are interpreted by a module called arabesque. Sometimes these are also called performances. [18:45] Samantha Wright: You can also trigger them from the command line with the command @do [18:45] Samantha Wright: It's very important to remember when you're not using local access on the system, there's no @ sign for commands. [18:46] Samantha Wright: This applies to remote console use, arabesque scripts, OEM presets, and when creating new devices and apps. [18:46] Presentation: Slide 33 [18:46] Samantha Wright: Making scripts, however, requires knowledge of how to manage the files on your controller. We'll talk about that next, as it's a versatile and useful skill for a number of tasks. [18:46] Presentation: Slide 34 [18:47] t3z: No chance of if x